[bot] Update Learning Hub: /model plan, Claude Opus 5, and Open Plugin Spec v1 - #2472
Merged
aaronpowell merged 1 commit intoJul 31, 2026
Merged
Conversation
- copilot-configuration-basics: document /model plan command (v1.0.74+) for per-phase model selection in plan mode, and note Claude Opus 5 availability - installing-and-using-plugins: add Open Plugin Spec v1 compatibility section documenting mcp.json bundle support (v1.0.74+) Sources: - https://github.com/github/copilot-cli/blob/main/changelog.md (v1.0.74, v1.0.75) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aaronpowell
approved these changes
Jul 31, 2026
Contributor
Author
|
🟡 Contributor Reputation Check: MEDIUM risk
Maintainers: please review this contributor before merging. |
github-actions
Bot
added
the
needs-review:MEDIUM
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Learning Hub documentation for recent Copilot CLI capabilities.
Changes:
- Documents Claude Opus 5 and plan-mode model selection.
- Adds Open Plugin Spec v1 and bundled MCP configuration guidance.
Show a summary per file
| File | Description |
|---|---|
copilot-configuration-basics.md |
Updates model-selection guidance. |
installing-and-using-plugins.md |
Documents Open Plugin Spec compatibility. |
Review details
Comments suppressed due to low confidence (3)
website/src/content/docs/learning-hub/installing-and-using-plugins.md:289
- Open Plugin Spec v1 defines exactly two portable component types: skills and MCP servers; agents are explicitly outside v1. Claiming that an Open Spec manifest makes the CLI discover bundled agents overstates the compatibility and will mislead authors into expecting agent portability.
The CLI reads the manifest, discovers the bundled agents, skills, and MCP server configuration, and integrates them the same way it handles native Copilot plugins.
website/src/content/docs/learning-hub/installing-and-using-plugins.md:293
- The Open Plugin Spec
mcp.jsonis not simply the same format as repository MCP files. V1 requires the top-level$schemaandmcpServersfields and constrains server transport types; repository examples in this site omit that schema and usetype: "local". Readers who copy an existing repository config could therefore produce a nonconforming plugin.
Open Plugin Spec v1 also standardizes how MCP server configuration is bundled in plugins. A plugin can now include an `mcp.json` file at its root to declare MCP servers it requires — using the same format as `.mcp.json` or `.github/mcp.json` in your repository. When you install such a plugin, its MCP server configuration is automatically merged into your active server list.
website/src/content/docs/learning-hub/installing-and-using-plugins.md:295
- This repeats the implication that agents are a portable Open Plugin Spec v1 component, but v1 only standardizes skills and MCP servers. Narrow the benefit to the components the standard actually covers.
This is useful for plugins that bundle dedicated tooling (for example, a database plugin that ships its own MCP server) — users get both the agent/skill and the required MCP server in a single install step.
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Balanced
|
|
||
| ``` | ||
| /model plan # open the picker to choose a model for plan mode | ||
| /model --plan claude-haiku # set a specific model for plan mode |
| If you encounter a plugin from the broader AI ecosystem (outside GitHub's own marketplace) that ships with an Open Plugin Spec v1 manifest, you can install it directly: | ||
|
|
||
| ```bash | ||
| copilot plugin install /path/to/openspec-plugin |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was found
Checking the GitHub Copilot CLI changelog for the past 7 days (July 21–28, 2026) surfaced three noteworthy updates:
/model plan(or/model --plan) to choose a separate model for plan mode, reverting to the session model on exitmcp.jsonconfiguration bundled in pluginsWhat was updated
copilot-configuration-basics.md/model plancommand, including examples of how to set, clear, and combine it with repository model pinninglastUpdatedto2026-07-28installing-and-using-plugins.mdmcp.jsonbundle format that allows plugins to ship their required MCP server configuration alongside agents/skills for a single-step installlastUpdatedto2026-07-28Source announcements
/model planand Open Plugin Spec v1